…AL-574]

Review of #1139 against the #1107/#1138 threads (plan/review-2026-09-11 §3.2).

- Type the fetch mocks as `vi.fn<typeof fetch>`: `vi.fn(async () => ...)` infers a
  zero-parameter mock, so every `mock.calls[i]?.[1]` assertion was a TS2493/TS2339
  under the repo's strict config. CI cannot see it (tests are excluded from `tsc`
  and biome does not typecheck), so it is checked with a throwaway tsconfig.
- `loading` starts `true` when the hook is about to fetch, so a host rendering
  `loading ? <Spinner/> : <Empty/>` no longer flashes the empty state on first paint.
- `refetch` is a no-op while the hook is disabled. It used to issue a real request
  whose result `parsed` then discarded in favour of `options.definitions`.
- JSDoc and README: `options.definitions` is compared by identity (pass a stable
  reference), a failed request keeps the previous results, and the zod boundary is
  pinned by a source-level check plus two tests, not by shipped runtime assertions.
- Name the map-enum `0..1` step `0.1` default as a product assumption and pin what
  keeps it safe: after the rebase onto `d658731b`, `min`/`max` are enforced through
  `validation` in `onChange` mode, but both that path and `getOutOfRangeParameterIds`
  are number-only, so a synthesized map-enum bound cannot reject a threshold map
  whose real range is different (harmful content is 0..6).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Integration branch only: it exists so a host can pin one preview package carrying
every open apollo stream. Not for merging into main.

Rebuilt on 2026-09-11 after the whole stack moved onto #1138's current head
(`d658731b`) and picked up a first pass of review fixes on #1139 and #1140. Reset to
`feat/apollo-react-guardrail-list` and re-merged `feat/apollo-react-guardrail-palette`
(#1147, AL-576).

The chip files both branches carry merged clean, being byte-identical again. Of the 17
conflicts, `i18n.ts`, `i18n.test.ts` and the 13 locale catalogs are unchanged on both
sides since the previous merge (`8856e4e0`), so its resolution was reused verbatim.
`index.ts` is the union of both barrels, biome-sorted, and checked for a lost export.
The README was rebuilt from `8856e4e0`'s merged copy with the three deltas since then
reapplied (the new base's, #1139's review fixes, #1140's review fixes), all cleanly, so
the sections still run along the data flow: definitions layer, list, palette, builder.

Verified after the merge: Guardrails suite 453 passing (26 files), tsc and biome clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…AL-574]

Review of #1139 against the #1107/#1138 threads (plan/review-2026-09-11 §3.2).

- Type the fetch mocks as `vi.fn<typeof fetch>`: `vi.fn(async () => ...)` infers a
  zero-parameter mock, so every `mock.calls[i]?.[1]` assertion was a TS2493/TS2339
  under the repo's strict config. CI cannot see it (tests are excluded from `tsc`
  and biome does not typecheck), so it is checked with a throwaway tsconfig.
- `loading` starts `true` when the hook is about to fetch, so a host rendering
  `loading ? <Spinner/> : <Empty/>` no longer flashes the empty state on first paint.
- `refetch` is a no-op while the hook is disabled. It used to issue a real request
  whose result `parsed` then discarded in favour of `options.definitions`.
- JSDoc and README: `options.definitions` is compared by identity (pass a stable
  reference), a failed request keeps the previous results, and the zod boundary is
  pinned by a source-level check plus two tests, not by shipped runtime assertions.
- Name the map-enum `0..1` step `0.1` default as a product assumption and pin what
  keeps it safe: after the rebase onto `d658731b`, `min`/`max` are enforced through
  `validation` in `onChange` mode, but both that path and `getOutOfRangeParameterIds`
  are number-only, so a synthesized map-enum bound cannot reject a threshold map
  whose real range is different (harmful content is 0..6).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailList`, the applied-guardrails list both products render under a
tool or an agent: rows with their lifecycle and status chips, BYO notices,
per-row edit and remove, drag reordering, and the empty state.

The host filters and the list renders. Items arrive already resolved against
their definitions, every callback is an intent, and `renderItemActions`,
`statusBanner` and `addSlot` are slots rather than product branches, so no
telemetry, flag or product type crosses the boundary. `GuardrailListItem` is a
structural mirror of what both products already hold.

Reordering is dnd-kit with `verticalListSortingStrategy`, restricted to the
vertical axis and the parent element (`@dnd-kit/modifiers`, the one new
dependency). The row transform is `CSS.Translate`, never `CSS.Transform`:
`useSortable` derives its layout transform from the row's before and after
rects, so with variable row heights (a description line, a BYO notice)
`CSS.Transform` emits a `scaleY` that visibly squashes or stretches the row's
text mid-animation. The strategy never produces a scale of its own, so dropping
it costs nothing. Verified against the installed `@dnd-kit/sortable` source,
which the published docs do not cover.

Rows highlight on hover unconditionally, like wind's `TableRow`: a row is a
hover target whether or not clicking it opens the editor. `rowActivatesEdit`
restores the legacy click-to-edit behaviour, and only then does the row body
carry `cursor-pointer` and its own focus ring, since only then is it a control.
The tint is `accent`, Apollo's hover surface (`--accent: var(--surface-hover)`),
not `muted`, which is `surface-overlay`, the panel the list usually sits on and
therefore invisible against it. The family-wide rule is in the README.

Seventeen `guardrails.list.*` lingui ids. Twelve take their English from Flow's
canvas catalog, so the wording is what the product already ships; the other
five have no host equivalent and are newly written here (`edit-row`,
`status-feature-disabled`, `status-disabled`, `status-unavailable`,
`administration-governance`), so they are the ones needing a real loc pass
rather than a lookup. English only, like every other string in this package:
`chore(l10n): sync from Localization` owns the other thirteen catalogs. The
i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and reader.

The "Preview" lifecycle chip takes the family's `info` tone, added to
`GuardrailStatusChip` on #1139 for this and the palette: blue is what both
products already give that chip (Flow's `InfoBadge tone="preview"`, Agents'
`PreviewChip` on `semantic.colorInfoBackground`), where this row shipped it
neutral grey.

`GuardrailStatusBanner` and `MixedScopesBanner` become public so a host can
compose the `statusBanner` slot, and each gains a story. `MixedScopesBanner`
also gains the `mt-0` the title-less alert fix should have given it: wind's
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below its icon. The same
hunk is on apollo-ui#1147 and apollo-ui#1161 so the three merge without a
conflict; the real fix is one line in wind's `alertVariants`.

`__fixtures__/**` is excluded from the rslib build alongside `src/test/**`:
fixtures are data for the suites, not API, and they reach for devDependencies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailPalette`, the picker both products open from their guardrails
list: grouped definitions, an optional create-custom entry, and the loading,
failed and empty states.

The host filters and the palette offers. Definitions arrive pre-filtered
(flags, entitlements, `FeatureDisabled`/`Disabled`, Tool scope), both callbacks
are intents, and no telemetry, flag or product type crosses the boundary.
Definitions are generic over the eight fields the palette reads, so
`EnrichedGuardrailDefinition` and a product's own type both go in and come back
out of `onSelectOotb` unchanged.

Grouping and entry identity are re-derived from what both products already
ship: one unheaded group in payload order without BYO definitions, otherwise a
group per BYO folder or connector plus a trailing UiPath group, and BYO entries
keyed by validator name and connection id. An `Unauthorised` definition is
offered, chipped and not choosable (`aria-disabled`, so it stays reachable),
which is Flow's behaviour; Agents lets it through to a builder that then
refuses to save. Two chips take harvested tones rather than neutral grey: the
bring-your-own connector chip is `success`, the green both products already give
it, and the "Preview" lifecycle chip is `info`, the blue both products give that
one (added to `GuardrailStatusChip` on #1139 for this and the list).

Entries are real buttons on wind's interactive-item idiom, not a `div` with
`role="listitem"` and its own key handler: hover is `bg-accent` gated on the
enabled branch, disabled is `opacity-50`, and the focus ring matches `Button`.
The palette is a single tab stop with roving focus, where Arrow/Home/End cross
group boundaries and `aria-disabled` entries are included so the `Unauthorised`
chip stays reachable. The focused entry is located from the keyboard event
target rather than `document.activeElement`, which retargets to the shadow host
inside Agents' shadow root and would make every arrow key a silent no-op there;
a test renders into an open shadow root and arrows down. Groups name themselves
with `aria-labelledby` pointing at the visible header rather than repeating it.

Only the picker ships. Flow's dialog and inline overlay and Agents' sidebar
takeover are host orchestration, shown in the stories rather than modelled in a
wrapper.

Nine `guardrails.palette.*` lingui ids, harvested from the two products' own
catalogs so the English is what they already ship. English only, like every
other string in this package: `chore(l10n): sync from Localization` owns the
other thirteen catalogs. The i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and file
reader. Three label resolvers now share one `mergeLabels` helper.

Also carries the title-less alert fix the sibling branches each need:
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below the icon. `mt-0` at
the call site, the same hunk as apollo-ui#1140 and apollo-ui#1161 so the three
merge without a conflict; the real fix belongs in apollo-wind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailList`, the applied-guardrails list both products render under a
tool or an agent: rows with their lifecycle and status chips, BYO notices,
per-row edit and remove, drag reordering, and the empty state.

The host filters and the list renders. Items arrive already resolved against
their definitions, every callback is an intent, and `renderItemActions`,
`statusBanner` and `addSlot` are slots rather than product branches, so no
telemetry, flag or product type crosses the boundary. `GuardrailListItem` is a
structural mirror of what both products already hold.

Reordering is dnd-kit with `verticalListSortingStrategy`, restricted to the
vertical axis and the parent element (`@dnd-kit/modifiers`, the one new
dependency). The row transform is `CSS.Translate`, never `CSS.Transform`:
`useSortable` derives its layout transform from the row's before and after
rects, so with variable row heights (a description line, a BYO notice)
`CSS.Transform` emits a `scaleY` that visibly squashes or stretches the row's
text mid-animation. The strategy never produces a scale of its own, so dropping
it costs nothing. Verified against the installed `@dnd-kit/sortable` source,
which the published docs do not cover.

Rows highlight on hover unconditionally, like wind's `TableRow`: a row is a
hover target whether or not clicking it opens the editor. `rowActivatesEdit`
restores the legacy click-to-edit behaviour, and only then does the row body
carry `cursor-pointer` and its own focus ring, since only then is it a control.
The tint is `accent`, Apollo's hover surface (`--accent: var(--surface-hover)`),
not `muted`, which is `surface-overlay`, the panel the list usually sits on and
therefore invisible against it. The family-wide rule is in the README.

Because the row paints that tint, the drag handle carries no negative margin:
`p-1` gives the row 4px, which is exactly the reach of the handle's
`ring-offset-2` focus ring, so pulling the handle out to align its glyph with
the row's leading edge put its hover surface and its ring outside the tinted
box. The glyph sits an icon button's worth of padding inside the edge instead.

Seventeen `guardrails.list.*` lingui ids. Twelve take their English from Flow's
canvas catalog, so the wording is what the product already ships; the other
five have no host equivalent and are newly written here (`edit-row`,
`status-feature-disabled`, `status-disabled`, `status-unavailable`,
`administration-governance`), so they are the ones needing a real loc pass
rather than a lookup. English only, like every other string in this package:
`chore(l10n): sync from Localization` owns the other thirteen catalogs. The
i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and reader.

The "Preview" lifecycle chip takes the family's `info` tone, added to
`GuardrailStatusChip` on #1139 for this and the palette: blue is what both
products already give that chip (Flow's `InfoBadge tone="preview"`, Agents'
`PreviewChip` on `semantic.colorInfoBackground`), where this row shipped it
neutral grey.

`GuardrailStatusBanner` and `MixedScopesBanner` become public so a host can
compose the `statusBanner` slot, and each gains a story. `MixedScopesBanner`
also gains the `mt-0` the title-less alert fix should have given it: wind's
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below its icon. The same
hunk is on apollo-ui#1147 and apollo-ui#1161 so the three merge without a
conflict; the real fix is one line in wind's `alertVariants`.

`__fixtures__/**` is excluded from the rslib build alongside `src/test/**`:
fixtures are data for the suites, not API, and they reach for devDependencies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailPalette`, the picker both products open from their guardrails
list: grouped definitions, an optional create-custom entry, and the loading,
failed and empty states.

The host filters and the palette offers. Definitions arrive pre-filtered
(flags, entitlements, `FeatureDisabled`/`Disabled`, Tool scope), both callbacks
are intents, and no telemetry, flag or product type crosses the boundary.
Definitions are generic over the eight fields the palette reads, so
`EnrichedGuardrailDefinition` and a product's own type both go in and come back
out of `onSelectOotb` unchanged.

Grouping and entry identity are re-derived from what both products already
ship: one unheaded group in payload order without BYO definitions, otherwise a
group per BYO folder or connector plus a trailing UiPath group, and BYO entries
keyed by validator name and connection id. An `Unauthorised` definition is
offered, chipped and not choosable (`aria-disabled`, so it stays reachable),
which is Flow's behaviour; Agents lets it through to a builder that then
refuses to save. Two chips take harvested tones rather than neutral grey: the
bring-your-own connector chip is `success`, the green both products already give
it, and the "Preview" lifecycle chip is `info`, the blue both products give that
one (added to `GuardrailStatusChip` on #1139 for this and the list).

Entries are real buttons on wind's interactive-item idiom, not a `div` with
`role="listitem"` and its own key handler: hover is `bg-accent` gated on the
enabled branch, disabled is `opacity-50`, and the focus ring matches `Button`.
The palette is a single tab stop with roving focus, where Arrow/Home/End cross
group boundaries and `aria-disabled` entries are included so the `Unauthorised`
chip stays reachable. The focused entry is located from the keyboard event
target rather than `document.activeElement`, which retargets to the shadow host
inside Agents' shadow root and would make every arrow key a silent no-op there;
a test renders into an open shadow root and arrows down. Groups name themselves
with `aria-labelledby` pointing at the visible header rather than repeating it.

Only the picker ships. Flow's dialog and inline overlay and Agents' sidebar
takeover are host orchestration, shown in the stories rather than modelled in a
wrapper.

Nine `guardrails.palette.*` lingui ids, harvested from the two products' own
catalogs so the English is what they already ship. English only, like every
other string in this package: `chore(l10n): sync from Localization` owns the
other thirteen catalogs. The i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and file
reader. Three label resolvers now share one `mergeLabels` helper.

Also carries the title-less alert fix the sibling branches each need:
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below the icon. `mt-0` at
the call site, the same hunk as apollo-ui#1140 and apollo-ui#1161 so the three
merge without a conflict; the real fix belongs in apollo-wind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailList`, the applied-guardrails list both products render under a
tool or an agent: rows with their lifecycle and status chips, BYO notices,
per-row edit and remove, drag reordering, and the empty state.

The host filters and the list renders. Items arrive already resolved against
their definitions, every callback is an intent, and `renderItemActions`,
`statusBanner` and `addSlot` are slots rather than product branches, so no
telemetry, flag or product type crosses the boundary. `GuardrailListItem` is a
structural mirror of what both products already hold.

Reordering is dnd-kit with `verticalListSortingStrategy`, restricted to the
vertical axis and the parent element (`@dnd-kit/modifiers`, the one new
dependency). The row transform is `CSS.Translate`, never `CSS.Transform`:
`useSortable` derives its layout transform from the row's before and after
rects, so with variable row heights (a description line, a BYO notice)
`CSS.Transform` emits a `scaleY` that visibly squashes or stretches the row's
text mid-animation. The strategy never produces a scale of its own, so dropping
it costs nothing. Verified against the installed `@dnd-kit/sortable` source,
which the published docs do not cover.

Rows highlight on hover unconditionally, like wind's `TableRow`: a row is a
hover target whether or not clicking it opens the editor. `rowActivatesEdit`
restores the legacy click-to-edit behaviour, and only then does the row body
carry `cursor-pointer` and its own focus ring, since only then is it a control.
The tint is `accent`, Apollo's hover surface (`--accent: var(--surface-hover)`),
not `muted`, which is `surface-overlay`, the panel the list usually sits on and
therefore invisible against it. The family-wide rule is in the README.

Because the row paints that tint, the drag handle carries no negative margin:
`p-1` gives the row 4px, which is exactly the reach of the handle's
`ring-offset-2` focus ring, so pulling the handle out to align its glyph with
the row's leading edge put its hover surface and its ring outside the tinted
box. The glyph sits an icon button's worth of padding inside the edge instead.

Seventeen `guardrails.list.*` lingui ids. Twelve take their English from Flow's
canvas catalog, so the wording is what the product already ships; the other
five have no host equivalent and are newly written here (`edit-row`,
`status-feature-disabled`, `status-disabled`, `status-unavailable`,
`administration-governance`), so they are the ones needing a real loc pass
rather than a lookup. English only, like every other string in this package:
`chore(l10n): sync from Localization` owns the other thirteen catalogs. The
i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and reader,
and the stories carry no Japanese example: with the translations gone it would
render English and claim otherwise.

The "Preview" lifecycle chip takes the family's `info` tone, added to
`GuardrailStatusChip` on #1139 for this and the palette: blue is what both
products already give that chip (Flow's `InfoBadge tone="preview"`, Agents'
`PreviewChip` on `semantic.colorInfoBackground`), where this row shipped it
neutral grey.

`GuardrailStatusBanner` and `MixedScopesBanner` become public so a host can
compose the `statusBanner` slot, and each gains a story. `MixedScopesBanner`
also gains the `mt-0` the title-less alert fix should have given it: wind's
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below its icon. The same
hunk is on apollo-ui#1147 and apollo-ui#1161 so the three merge without a
conflict; the real fix is one line in wind's `alertVariants`.

`__fixtures__/**` is excluded from the rslib build alongside `src/test/**`:
fixtures are data for the suites, not API, and they reach for devDependencies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailPalette`, the picker both products open from their guardrails
list: grouped definitions, an optional create-custom entry, and the loading,
failed and empty states.

The host filters and the palette offers. Definitions arrive pre-filtered
(flags, entitlements, `FeatureDisabled`/`Disabled`, Tool scope), both callbacks
are intents, and no telemetry, flag or product type crosses the boundary.
Definitions are generic over the eight fields the palette reads, so
`EnrichedGuardrailDefinition` and a product's own type both go in and come back
out of `onSelectOotb` unchanged.

Grouping and entry identity are re-derived from what both products already
ship: one unheaded group in payload order without BYO definitions, otherwise a
group per BYO folder or connector plus a trailing UiPath group, and BYO entries
keyed by validator name and connection id. An `Unauthorised` definition is
offered, chipped and not choosable (`aria-disabled`, so it stays reachable),
which is Flow's behaviour; Agents lets it through to a builder that then
refuses to save. Two chips take harvested tones rather than neutral grey: the
bring-your-own connector chip is `success`, the green both products already give
it, and the "Preview" lifecycle chip is `info`, the blue both products give that
one (added to `GuardrailStatusChip` on #1139 for this and the list).

Entries are real buttons on wind's interactive-item idiom, not a `div` with
`role="listitem"` and its own key handler: hover is `bg-accent` gated on the
enabled branch, disabled is `opacity-50`, and the focus ring matches `Button`.
The palette is a single tab stop with roving focus, where Arrow/Home/End cross
group boundaries and `aria-disabled` entries are included so the `Unauthorised`
chip stays reachable. The focused entry is located from the keyboard event
target rather than `document.activeElement`, which retargets to the shadow host
inside Agents' shadow root and would make every arrow key a silent no-op there;
a test renders into an open shadow root and arrows down. Groups name themselves
with `aria-labelledby` pointing at the visible header rather than repeating it.

Only the picker ships. Flow's dialog and inline overlay and Agents' sidebar
takeover are host orchestration, shown in the stories rather than modelled in a
wrapper.

Nine `guardrails.palette.*` lingui ids, harvested from the two products' own
catalogs so the English is what they already ship. English only, like every
other string in this package: `chore(l10n): sync from Localization` owns the
other thirteen catalogs. The i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and file
reader. Three label resolvers now share one `mergeLabels` helper.

Also carries the title-less alert fix the sibling branches each need:
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below the icon. `mt-0` at
the call site, the same hunk as apollo-ui#1140 and apollo-ui#1161 so the three
merge without a conflict; the real fix belongs in apollo-wind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailList`, the applied-guardrails list both products render under a
tool or an agent: rows with their lifecycle and status chips, BYO notices,
per-row edit and remove, drag reordering, and the empty state.

The host filters and the list renders. Items arrive already resolved against
their definitions, every callback is an intent, and `renderItemActions`,
`statusBanner` and `addSlot` are slots rather than product branches, so no
telemetry, flag or product type crosses the boundary. `GuardrailListItem` is a
structural mirror of what both products already hold.

Reordering is dnd-kit with `verticalListSortingStrategy`, restricted to the
vertical axis and the parent element (`@dnd-kit/modifiers`, the one new
dependency). The row transform is `CSS.Translate`, never `CSS.Transform`:
`useSortable` derives its layout transform from the row's before and after
rects, so with variable row heights (a description line, a BYO notice)
`CSS.Transform` emits a `scaleY` that visibly squashes or stretches the row's
text mid-animation. The strategy never produces a scale of its own, so dropping
it costs nothing. Verified against the installed `@dnd-kit/sortable` source,
which the published docs do not cover.

Rows highlight on hover unconditionally, like wind's `TableRow`: a row is a
hover target whether or not clicking it opens the editor. `rowActivatesEdit`
restores the legacy click-to-edit behaviour, and only then does the row body
carry `cursor-pointer` and its own focus ring, since only then is it a control.
The tint is `accent`, Apollo's hover surface (`--accent: var(--surface-hover)`),
not `muted`, which is `surface-overlay`, the panel the list usually sits on and
therefore invisible against it. The family-wide rule is in the README.

Because the row paints that tint, the drag handle carries no negative margin:
`p-1` gives the row 4px, which is exactly the reach of the handle's
`ring-offset-2` focus ring, so pulling the handle out to align its glyph with
the row's leading edge put its hover surface and its ring outside the tinted
box. The glyph sits an icon button's worth of padding inside the edge instead.

Seventeen `guardrails.list.*` lingui ids. Twelve take their English from Flow's
canvas catalog, so the wording is what the product already ships; the other
five have no host equivalent and are newly written here (`edit-row`,
`status-feature-disabled`, `status-disabled`, `status-unavailable`,
`administration-governance`), so they are the ones needing a real loc pass
rather than a lookup. English only, like every other string in this package:
`chore(l10n): sync from Localization` owns the other thirteen catalogs. The
i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and reader,
and the stories carry no Japanese example: with the translations gone it would
render English and claim otherwise.

The "Preview" lifecycle chip takes the family's `info` tone, added to
`GuardrailStatusChip` on #1139 for this and the palette: blue is what both
products already give that chip (Flow's `InfoBadge tone="preview"`, Agents'
`PreviewChip` on `semantic.colorInfoBackground`), where this row shipped it
neutral grey.

`GuardrailStatusBanner` and `MixedScopesBanner` become public so a host can
compose the `statusBanner` slot, and each gains a story. `MixedScopesBanner`
also gains the `mt-0` the title-less alert fix should have given it: wind's
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below its icon. The same
hunk is on apollo-ui#1147 and apollo-ui#1161 so the three merge without a
conflict; the real fix is one line in wind's `alertVariants`.

`__fixtures__/**` is excluded from the rslib build alongside `src/test/**`:
fixtures are data for the suites, not API, and they reach for devDependencies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailPalette`, the picker both products open from their guardrails
list: grouped definitions, an optional create-custom entry, and the loading,
failed and empty states.

The host filters and the palette offers. Definitions arrive pre-filtered
(flags, entitlements, `FeatureDisabled`/`Disabled`, Tool scope), both callbacks
are intents, and no telemetry, flag or product type crosses the boundary.
Definitions are generic over the eight fields the palette reads, so
`EnrichedGuardrailDefinition` and a product's own type both go in and come back
out of `onSelectOotb` unchanged.

Grouping and entry identity are re-derived from what both products already
ship: one unheaded group in payload order without BYO definitions, otherwise a
group per BYO folder or connector plus a trailing UiPath group, and BYO entries
keyed by validator name and connection id. An `Unauthorised` definition is
offered, chipped and not choosable (`aria-disabled`, so it stays reachable),
which is Flow's behaviour; Agents lets it through to a builder that then
refuses to save. Two chips take harvested tones rather than neutral grey: the
bring-your-own connector chip is `success`, the green both products already give
it, and the "Preview" lifecycle chip is `info`, the blue both products give that
one (added to `GuardrailStatusChip` on #1139 for this and the list).

Entries are real buttons on wind's interactive-item idiom, not a `div` with
`role="listitem"` and its own key handler: hover is `bg-accent` gated on the
enabled branch, disabled is `opacity-50`, and the focus ring matches `Button`.
The palette is a single tab stop with roving focus, where Arrow/Home/End cross
group boundaries and `aria-disabled` entries are included so the `Unauthorised`
chip stays reachable. The focused entry is located from the keyboard event
target rather than `document.activeElement`, which retargets to the shadow host
inside Agents' shadow root and would make every arrow key a silent no-op there;
a test renders into an open shadow root and arrows down. Groups name themselves
with `aria-labelledby` pointing at the visible header rather than repeating it.

Only the picker ships. Flow's dialog and inline overlay and Agents' sidebar
takeover are host orchestration, shown in the stories rather than modelled in a
wrapper.

Nine `guardrails.palette.*` lingui ids, harvested from the two products' own
catalogs so the English is what they already ship. English only, like every
other string in this package: `chore(l10n): sync from Localization` owns the
other thirteen catalogs. The i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and file
reader. Three label resolvers now share one `mergeLabels` helper.

Also carries the title-less alert fix the sibling branches each need:
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below the icon. `mt-0` at
the call site, the same hunk as apollo-ui#1140 and apollo-ui#1161 so the three
merge without a conflict; the real fix belongs in apollo-wind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailList`, the applied-guardrails list both products render under a
tool or an agent: rows with their lifecycle and status chips, BYO notices,
per-row edit and remove, drag reordering, and the empty state.

The host filters and the list renders. Items arrive already resolved against
their definitions, every callback is an intent, and `renderItemActions`,
`statusBanner` and `addSlot` are slots rather than product branches, so no
telemetry, flag or product type crosses the boundary. `GuardrailListItem` is a
structural mirror of what both products already hold.

Reordering is dnd-kit with `verticalListSortingStrategy`, restricted to the
vertical axis and the parent element (`@dnd-kit/modifiers`, the one new
dependency). The row transform is `CSS.Translate`, never `CSS.Transform`:
`useSortable` derives its layout transform from the row's before and after
rects, so with variable row heights (a description line, a BYO notice)
`CSS.Transform` emits a `scaleY` that visibly squashes or stretches the row's
text mid-animation. The strategy never produces a scale of its own, so dropping
it costs nothing. Verified against the installed `@dnd-kit/sortable` source,
which the published docs do not cover.

Rows highlight on hover unconditionally, like wind's `TableRow`: a row is a
hover target whether or not clicking it opens the editor. `rowActivatesEdit`
restores the legacy click-to-edit behaviour, and only then does the row body
carry `cursor-pointer` and its own focus ring, since only then is it a control.
The tint is `accent`, Apollo's hover surface (`--accent: var(--surface-hover)`),
not `muted`, which is `surface-overlay`, the panel the list usually sits on and
therefore invisible against it. The family-wide rule is in the README.

Because the row paints that tint, the drag handle carries no negative margin:
`p-1` gives the row 4px, which is exactly the reach of the handle's
`ring-offset-2` focus ring, so pulling the handle out to align its glyph with
the row's leading edge put its hover surface and its ring outside the tinted
box. The glyph sits an icon button's worth of padding inside the edge instead.

Seventeen `guardrails.list.*` lingui ids. Twelve take their English from Flow's
canvas catalog, so the wording is what the product already ships; the other
five have no host equivalent and are newly written here (`edit-row`,
`status-feature-disabled`, `status-disabled`, `status-unavailable`,
`administration-governance`), so they are the ones needing a real loc pass
rather than a lookup. English only, like every other string in this package:
`chore(l10n): sync from Localization` owns the other thirteen catalogs. The
i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and reader,
and the stories carry no Japanese example: with the translations gone it would
render English and claim otherwise.

The "Preview" lifecycle chip takes the family's `info` tone, added to
`GuardrailStatusChip` on #1139 for this and the palette: blue is what both
products already give that chip (Flow's `InfoBadge tone="preview"`, Agents'
`PreviewChip` on `semantic.colorInfoBackground`), where this row shipped it
neutral grey.

`GuardrailStatusBanner` and `MixedScopesBanner` become public so a host can
compose the `statusBanner` slot, and each gains a story. `MixedScopesBanner`
also gains the `mt-0` the title-less alert fix should have given it: wind's
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below its icon. The same
hunk is on apollo-ui#1147 and apollo-ui#1161 so the three merge without a
conflict; the real fix is one line in wind's `alertVariants`.

`__fixtures__/**` is excluded from the rslib build alongside `src/test/**`:
fixtures are data for the suites, not API, and they reach for devDependencies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Add `GuardrailPalette`, the picker both products open from their guardrails
list: grouped definitions, an optional create-custom entry, and the loading,
failed and empty states.

The host filters and the palette offers. Definitions arrive pre-filtered
(flags, entitlements, `FeatureDisabled`/`Disabled`, Tool scope), both callbacks
are intents, and no telemetry, flag or product type crosses the boundary.
Definitions are generic over the eight fields the palette reads, so
`EnrichedGuardrailDefinition` and a product's own type both go in and come back
out of `onSelectOotb` unchanged.

Grouping and entry identity are re-derived from what both products already
ship: one unheaded group in payload order without BYO definitions, otherwise a
group per BYO folder or connector plus a trailing UiPath group, and BYO entries
keyed by validator name and connection id. An `Unauthorised` definition is
offered, chipped and not choosable (`aria-disabled`, so it stays reachable),
which is Flow's behaviour; Agents lets it through to a builder that then
refuses to save. Two chips take harvested tones rather than neutral grey: the
bring-your-own connector chip is `success`, the green both products already give
it, and the "Preview" lifecycle chip is `info`, the blue both products give that
one (added to `GuardrailStatusChip` on #1139 for this and the list).

Entries are real buttons on wind's interactive-item idiom, not a `div` with
`role="listitem"` and its own key handler: hover is `bg-accent` gated on the
enabled branch, disabled is `opacity-50`, and the focus ring matches `Button`.
The palette is a single tab stop with roving focus, where Arrow/Home/End cross
group boundaries and `aria-disabled` entries are included so the `Unauthorised`
chip stays reachable. The focused entry is located from the keyboard event
target rather than `document.activeElement`, which retargets to the shadow host
inside Agents' shadow root and would make every arrow key a silent no-op there;
a test renders into an open shadow root and arrows down. Groups name themselves
with `aria-labelledby` pointing at the visible header rather than repeating it.

Only the picker ships. Flow's dialog and inline overlay and Agents' sidebar
takeover are host orchestration, shown in the stories rather than modelled in a
wrapper.

Nine `guardrails.palette.*` lingui ids, harvested from the two products' own
catalogs so the English is what they already ship. English only, like every
other string in this package: `chore(l10n): sync from Localization` owns the
other thirteen catalogs. The i18n test uses the family's shared catalog scans
(`__fixtures__/catalog-coverage`) rather than its own locale list and file
reader. Three label resolvers now share one `mergeLabels` helper.

Also carries the title-less alert fix the sibling branches each need:
`AlertDescription` is unconditionally `mt-1`, which assumes an `AlertTitle`
above it, so a title-less alert renders its text 4px below the icon. `mt-0` at
the call site, the same hunk as apollo-ui#1140 and apollo-ui#1161 so the three
merge without a conflict; the real fix belongs in apollo-wind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>